home *** CD-ROM | disk | FTP | other *** search
- Path: SPOD2.dev.esoc.esa.de!328PT
- From: 328pt@SPOD2.dev.esoc.esa.de (Phil Tregoning)
- Newsgroups: comp.lang.c
- Subject: Re: Please help ?!
- Date: 28 Jan 1996 20:23:33 GMT
- Organization: European Space Operations Center
- Message-ID: <4egm05$1da3@info.estec.esa.nl>
- References: <4dm889$3hs@neptunus.pi.net> <4drnv1$cr@news.iag.net> <4drq5i$cr@news.iag.net> <4e6hse$dvl@ns.RezoNet.NET> <310a2389.49571776@nntp.ix.netcom.com> <4eg6h8$1db5@info.estec.esa.nl> <TANMOY.96Jan28100725@qcd.lanl.gov>
- Reply-To: 328pt@SPOD2.dev.esoc.esa.de
- NNTP-Posting-Host: spod2.dev.esoc.esa.de
-
-
- tanmoy@qcd.lanl.gov (Tanmoy Bhattacharya) writes:
-
- [Talk about casting return from malloc() when stdlib.h is not
- #include'd]
-
- >[...] The compiler _need not_ warn about an undeclared
- >function (i.e. such a warning is not mandated by ANSI: no warning is
- >however ever prohibited). Converting an int to a pointer without a
- >cast, however, needs a warning. On such compilers, then, avoiding the
- >cast can often help spot a fatal error.
-
- Does converting one type of pointer to another (excluding void *)
- without an appropriate cast require a warning, or is that also up
- to the compliler ? K&R2 says this is illegal.
-
- I agreed with everything else said, but I have yet to write anything
- that that could be called "magnificient products of art".
-
- Phil Tregoning
-